Problem description
ApexSQL Log is unable to remotely connect to Microsoft SQL Server 2008/2008 R2 (x86/x64/IA64) editions.
ApexSQL Log becomes sluggish or unresponsive when the audited transaction log chain is incomplete
Applies to
Problem description
ApexSQL Log is unable to finish reading or auditing large data sources.
Indexes rebuild operations are not properly replicated
Applies to:
Brief description:
Replicating “Rebuild index” DDL operation (creating a redo script) with ApexSQL Log will:
- Create phantom insert statement in transaction log auditing results and apply them to replica
- Report job failure when tables with no primary keys are affected
Server-side components installation is repeatedly prompted in loop, even when already installed
Applies to
Brief description
Server-side components installation is forced indefinitely even when server-side components are already installed on the machine hosting a SQL Server instance the tool is connecting to
The ‘Unknown error has occurred. Please see %AppData%\Local\ApexSQL\<ApexSQL application name>\crash.txt’ error is encountered when starting application
Applies to
ApexSQL Log, ApexSQL Recover
Summary
This article explains how to resolve an issue which prevents ApexSQL Log or ApexSQL Recover from starting. When either application is launched, the ‘Unknown error has occurred. Please see %AppData%\Local\ApexSQL\<application name>\crash.txt’ error is encountered, and application fails to start.
The ALM files are bulking up and using too much space
Applies to
ApexSQL Log
Summary
This article explains what to do when ApexSQL Log temporary files (.ALM type files) take too much space or when the number of .ALM files is too great
How to manually install and uninstall ApexSQL Log 2014 server side-components
Applies to
ApexSQL Log 2014
Summary
This article explains how to manually install and uninstall the server side components when it is not possible to utilize ApexSQL Log installer or when server side components need to be (un)installed on the passive cluster node.
The ‘Sqlcmd: Error: Syntax error at line XYZ near command ‘X’ in file ‘file_name.sql’.’ error is encountered when running SQL script via sqlcmd utility
Applies to
ApexSQL Recover, ApexSQL Log
Summary
This article explains how to manually edit script created by ApexSQL Recover or ApexSQL Log which contains ‘$’ sign in order for it to be executable by sqlcmd
ApexSQL Log shows the “Unknown recovery model” message and cannot connect to the database
Applies to
ApexSQL Log 2014
Summary
This article explains what to do when ApexSQL Log cannot connect to the database and reports that the database recovery model is unknown.
ApexSQL Log doesn’t recover non-index column updates in a clustered table
Applies to
ApexSQL Log
Summary
When reconstructing updates using ApexSQL Log in a table with a clustered index on multiple columns, update reconstruction fails for the non-index columns.
